System Groovy Plug-ins Groovy Plug-ins viewAdministration System Groovy Plug-ins Groovy Plug-ins view
The Groovy Plug-ins view displays any custom Groovy classes that you define for your site. Groovy plug-ins provide a powerful extension of N4. You can extend the system by inserting custom code and then triggering the code to execute by sending a JMS message into the system or by invoking it through a Web Service call.
To deploy a Groovy plug-in, you must add it as a code extension in the Code Extensions view (on page 1).
In the list view, the Id column displays the Groovy class name and the Short Desc column displays a short description of the class.
You can add, edit, and delete custom-defined Groovy classes from this view. In addition, you can use the Actions menu to:
Export SNX File: Export the selected Groovy classes as an XML file using the snx.xsd format.
Copy Reference Set: Copy Groovy classes from another entity set.
Compile Groovy Plug-ins: Compile the selected Groovy plug-in(s) and ensure that they are compatible with the N4 system on which they are deployed.
You must select at least one Groovy plug-in in the list view to access this action.
N4 compiles the selected Groovy plug-in(s) and displays the status and errors, if any, in the Summary of Groovy Compilation form.
A pre-deployed plug-in is a sample intended for you to copy and use as a template for your own plug-in that performs a similar function. These plug-ins cannot be edited or deleted.
Customer acknowledges that any external development created by Navis, Customer, or any third party which utilizes Groovy or any other programming language ("External Development"), is considered a modification or enhancement to Navis's generally available Software and will not be supported under Navis's standard Maintenance and Support program. Customer may retain Navis Services to assist in the maintenance and support of such code at the then current time and materials rates. Additionally, Customer acknowledges that the use of any development documentation provided by Navis ("Documentation") is for educational purposes only and at Customer's sole risk. Navis disclaims all warranties and/or conditions, whether express or implied, regarding External Development and/or Documentation, including but not limited to those of completeness or fitness for any particular purpose. Navis reserves the right to change the code extension API's and/or Documentation at any time.
If Navis updates a pre-deployed plug-in, the new version will overwrite the older version at installation. Therefore, we strongly recommend that you do not use these pre-deployed plug-ins directly.
If you have upgraded to N4 version 2.1 from an earlier version and you have any plug-ins or notifications for the UNIT_YARD_MOVE event, you should consider whether or not to include the new UNIT_YARD_SHIFT event. For more information on these events, see Yard events.
If you have Groovy code that uses the RoadCustomInitialzer Groovy Plug-in, then you must migrate this code to a SERVER_LIFECYCLE (on page 1) type code extension and delete the RoadCustomInitialzer plug-in. The RoadCustomInitializer plug-in was deprecated in N4 version 2.4. For more information, see the Pre-installation upgrade tasks in the Navis N4: Installation Guide for Windows or Navis N4: Installation Guide for Linux.
To add a new record:
Click 
.
To edit or delete a record:
In the list view, select the record(s) that you want to edit or delete.
Do one of the following:
Click 
to edit a selected record.
Click 
to delete the selected record(s).
|
Short Label |
Long Label |
In Filter? |
Sorting? |
|---|---|---|---|
|
App Version |
Application Version |
|
|
|
Changed |
Changed |
X |
X |
|
Changer |
Changer |
X |
X |
|
Created |
Created |
X |
X |
|
Creator |
Creator |
X |
X |
|
Id |
Id |
X |
X |
|
Pre deployed |
Is pre deployed |
X |
X |
|
Revision |
External Revision |
|
|
|
Short Desc |
Short Description |
X |
X |
|
Signature |
Signature |
|
|
|
Signature Summary |
Signature Summary |
|
|
|
Verified |
Verified |
|
|